ring_buffer: Use cached allocation for ring_buffer stream data #10315
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
_data_buffer should always be allocated as cached. It became uncached (when is_shared==true) by mistake as a result of a regression introduced by this commit: d519e7e. This restores the original cached allocation behaviour for _data_buffer. Signed-off-by: Serhiy Katsyuba <serhiy.katsyuba@intel.com>
serhiy-katsyuba-intel
requested review from
dbaluta,
kv2019i,
lbetlej,
lgirdwood,
mmaka1 and
plbossart
as code owners
serhiy-katsyuba-intel
requested review from
abonislawski,
softwarecki and
tmleman
tmleman
approved these changes
Oct 21, 2025
softwarecki
approved these changes
Oct 21, 2025
abonislawski
approved these changes
Oct 23, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
_data_buffer should always be allocated as cached. It became uncached (when is_shared==true) by mistake as a result of a regression introduced by this commit: d519e7e.
This restores the original cached allocation behaviour for _data_buffer.